Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make ale linter configurable #52

Closed
wants to merge 1 commit into from

Conversation

fanzeyi
Copy link

@fanzeyi fanzeyi commented Apr 12, 2019

This pull request adds two options for configuring ALE beancount linter, g:ale_beancount_bean_check_executable and g:ale_beancount_bean_check_options.

The motivation of having this configurable is because I'm using multiple files in my beancount bookkeeping while the default bean-check won't check other files for account information. This ends up with many error messages "Invalid reference to unknown account". With the ability to configure the path to the executable, I'm able to write a bean-check wrapper to make it recognize my project structure.

@kodonnell
Copy link

Out of interest, what are your values for your two options to make this work for your multiple beancount files, and what's your 'bean-check wrapper'? I've got the same problem, but am wondering whether you could automatically use b:beancount_root and turn your 'beancount wrapper' into an internal vim function that works with Ale? (Which should just be running bean-check on the b:beancount_root and filtering to messages only from the current file, right?) Sorry, I'm new to beancount and Ale (and, well, vim), so apologies if that is unintelligent.

@fanzeyi
Copy link
Author

fanzeyi commented May 26, 2019

@kodonnell nothing fancy. It's just pointing to a shell script that runs bean-check with my entry beancount file.

@fanzeyi fanzeyi closed this Aug 28, 2019
@fanzeyi fanzeyi deleted the ale-linter-configuration branch August 28, 2019 03:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants